\chapterEt{Conclusion}

First of all, the file access vulnerability should have been avoided by restricting the traversal right out of the website repository, it's not only a \css potential exposure, it's an administration negligence.

Moreover, the \css injections can be avoided by sanitazing every input that the programs uses. Of course, it asked more efforts from the developpers part but this is the price for a more secure software.

In conclusion, even if \css vulnerabilities are still an important part of the vulnerability panel, there are now consistent parser and scanner to make the developpement easier and restrict there impacts.
 

